ENH: prompt user to update deployment docs, providing the necessary info to do so #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
After running the ansible script, prompt the user to update the deployment documentation.
Motivation and Context
I'd like to keep the current deployments docs page as up-to-date as possible to keep track of our deployments. Doing this as we go is more likely to succeed than trying to run after the information later. Providing all the info needed so the engineer doesn't need to go digging for anything should get us to a point of minimum barrier of entry.
How Has This Been Tested?
Interactively only
Where Has This Been Documented?
This is mentioned on the plc setup page, the ansible workflows page, and on the current deployments docs page (all on confluence)
Pre-merge checklist